Hi, |
Re: Read Locked Data Some time ago, Telelogic had a customer complain that while they could prevent certain folks from seeing certain objects and certain attributes, they could still see changes in History which defeated the purpose. So Telelogic did this: if the user has no 'R' access to the Attribute or the Object, then they get 'read locked' History records. Now what they actually implemented was "If the user has no CURRENT 'R' access...". that means if an object is purged or an attribute deleted or renamed, then nobody has CURRENT 'R' access because it doesn't exist, and everyone will get read locked data in History. (Well, everybody except the 'Administrator'). I digress: ... in v4 of DOORS they had a similar problem with Passwords. While the 'Password' attribute in the invisible 'Users' module was write-only, you could still view password changes in History... You can test that by creating some attr and noticing its in History; but when you delete the attr then both History records are Read Locked. One can still cleverly get around that by creating the attribute in question, view History, then close the module without saving it. If you are not deleting or renaming attributes (or objects) you should see the History of your changes.
|